Skip to content

Fix typo in configuring-scim-provisioning-with-okta.md#38289

Merged
Sharra-writes merged 2 commits intogithub:mainfrom
tinchomengo:patch-1
May 20, 2025
Merged

Fix typo in configuring-scim-provisioning-with-okta.md#38289
Sharra-writes merged 2 commits intogithub:mainfrom
tinchomengo:patch-1

Conversation

@tinchomengo
Copy link
Copy Markdown
Contributor

@tinchomengo tinchomengo commented May 15, 2025

[No issue — typo fix spotted while reading documentation]

What's being changed:

This PR fixes a minor typo in the documentation.

Page: Configuring SCIM provisioning with Okta
Before: “assigned to the the GitHub Enterprise Managed User application...”
After: “assigned to the GitHub Enterprise Managed User application...”

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. (As this is a simple typo, no SME review is required.)
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@welcome
Copy link
Copy Markdown

welcome bot commented May 15, 2025

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label May 15, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented May 15, 2025 •
edited
Loading

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-with-okta.md ghec
ghes@ 3.17 3.16 3.15 3.14
ghec
ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@tinchomengo tinchomengo changed the title Update configuring-scim-provisioning-with-okta.md Fix typo in configuring-scim-provisioning-with-okta.md May 15, 2025
@Sharra-writes Sharra-writes added content This issue or pull request belongs to the Docs Content team and removed triage Do not begin working on this issue until triaged by the team labels May 15, 2025
@Sharra-writes
Copy link
Copy Markdown
Contributor

Sharra-writes commented May 15, 2025

Thanks for opening a PR! I think this has some versioning weirdness, so let me double check that it shouldn't be the second "the" that gets deleted.

@Sharra-writes
Copy link
Copy Markdown
Contributor

Sharra-writes commented May 20, 2025

@tinchomengo Sorry, this got a little lost in the shuffle last week. But I've previewed it and it looks good! I'll get it added to the merge queue once checks are passing.

@Sharra-writes Sharra-writes added this pull request to the merge queue May 20, 2025
Merged via the queue into github:main with commit 11d1c39 May 20, 2025
42 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented May 20, 2025

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Sharra-writes Sharra-writes Sharra-writes approved these changes

Assignees

No one assigned

Labels

content This issue or pull request belongs to the Docs Content team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@tinchomengo @Sharra-writes